\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\fc0 is shareware. Oceania feels strongly about the shareware/freeware concept of program distribution. We have seen little shareware for the NeXT, and would like to see that change. In order for you to help this change, you, the program user, are required to do two things:\
1) Freely distribute this program. Anybody can have it, and try it out for free.\
2) Evaluate the program for free. Try using it for a sample project. See how you like it.\
3) If you keep the program and use it (more than a month), send a shareware fee of $20.00 to Oceania Health Care Systems.\
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\fc0 and pay for it, future products will be released this way. If you use it for free, future products will have "demo" modes, time-outs, and licenses. \
\b SEND SHAREWARE FEE OF $20.00 TO:
\b0 \
Oceania Health Care Systems\
325 Lytton Ave. Suite 400\
Palo Alto, CA 94301\
\b PRODUCT SUPPORT:
\b0 \
This product is offered with no support, express or implied. This product is offered "as-is". Any Shareware users will be registered with Oceania, Registered CheckItOut users are entitled to use any CheckItOut product upgrades at no additional cost, and will have access to pre-release and Beta test information about future Shareware products.\
Note that this is an "internal product" developed by John Robison. The more shareware payments we receive, the better my case is to continue to enhance the product.\
\b STANDARD DISCLAIMERS
\b0 \
This product is offered with no warranty, express or implied. This product is offered "as-is". You may NOT charge a fee for duplication of this product. Oceania Health Care Systems retains the sole rights to charge a fee for this product.
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\fc0 can not be sold or distributed on/in any media for profit (including mail order) without the prior express written consent of Oceania Health Care Systems. When distributed, this document must accompany
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\fc0 implies this agreement is understood and abided by.\
NO WARRANTY
\b0 \
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. OCEANIA HEALTH CARE SYSTEMS PROVIDES THIS PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.\
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\fc0 is based on the UNIX rcs (Revision Control System) programs. This program is basically a NeXTStep front end to using the ci and co commands for UNIX rcs. The Check In and the Check Out buttons do exactly that. These commands require that an RCS file has been previously initialized through the RCS initialization routine. This feature has now been incorporated into
\pard\tx1140\tx2300\tx3440\tx4600\tx5760\tx6900\tx8060\tx9200\tx10360\tx11520\fc0 Note that the current version of CheckItOut, CheckItOut 3.0, has a completely re-designed User Interface.
\pard\tx1140\tx2300\tx3440\tx4600\tx5760\tx6900\tx8060\tx9200\tx10360\tx11520\fc0 has a totally re-designed User Interface. It is also distributed as a .app directory. In addition, you can save and double-click project files. These files are saved with a ".cio" extension. CheckItOut now also supports "Smart uuencode". This feature allows a mixture of ASCII and non-ASCII files in the same project, with CheckItOut figuring out which is which. Countless other things were refined and tweaked to be more robust and consistent with RCS.\
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\b\fc0 INITIALIZATION OF RCS FILES:
\b0 \
You may need to initialize an RCS file before you first check in a file. You will get a warning message if this is the case. You may then choose the initialize button to create an RCS template file as necessary. The panel prompts for default locking and a user login access list. Note that the logins must be
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\fc0 from version 2.0. Initialize now automatically sets up the rcs template for the file, then loads the current file into the template as RCS version 1.0.\
\b PREFERENCES:\
\b0 \
HIDE ON AUTO-LAUNCH - (Currently not implemented)\
If this box is checked, CheckItOut will automatically hide itself when Auto-Launched from the Workspace. This feature allows you to always launch CheckItOut when
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\fc0 in, but only see it when you really need it.\
VERBOSE CONSOLE MESSAGES\
When this box is checked, all RCS commands are executed normally. If this box is unchecked, CheckItOut adds a "-q" to all RCS commands. You may access the diagnostics information by opening the console under the Tools menu of NeXT's Workspace application. It is a good idea to have the console open if you encounter warnings or errors when using CheckItOut. All the RCS messages are currently printed in this location.\
UUENCODE ALL FILES\
This option is retained for compatibility with CheckItOut2 (CheckItOut version 2.0). In the version 2.0, if one of the files in a project was non-ASCII, they all had to be uuencoded. Version 3.0 now supports a "smart" uuencode. This allows for ASCII files to remain ASCII. Non-ASCII files are automatically encoded.\
SUFFIX DEFAULTS\
This is the heart of version 3.0 - "Smart uuencode". You can manually add these items, or
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\fc0 , allow CheckItOut to add them for you. (Remember to include the "dot" and add semicolon separators if you do this yourself.) Whenever CheckItOut encounters a new suffix, it will try to guess the type of file, then provide you with an alert panel to verify this guess. Once verified, the suffix is added to these defaults, and remembered for the life of CheckItOut. This feature allows you to use RCS for all plain ASCII files, but also allows for some version control in non-ASCII files. \
\b OTHER INFORMATION:\
\b0 \
RCS WARNINGS and ERRORS\
Errors (regardless of Diagnostics/Quiet mode) are written to the console. When using Diagnostics mode, warnings are also written. This happens even when the Workspace Console window is closed. The NeXT computer (with 2.0 Software) writes all messages to a console.log file in /tmp. Do not be surprised if there are several messages here if you have been working on several projects. In addition, the CheckItOut console keeps a very terse accounting of your session. You can clean the current CheckItOut console at any time from the menu.\
LOG MESSAGE\
The check in log message is added by the use of the "-m" option for ci. You are prompted for a log message in which the log message text field is blank. If you click done (or hit return) your file will be checked in without a log message. You are limited in your amount of text using this log panel. You may click done or more conveniently hit return at the end of your log message. Quotes are currently not supported in this panel.\
FILES AND PERMISSIONS IN YOUR DIRECTORY\
When checking out a file, if you already have files in that directory, they will be overwritten with the checked out versions of the same files. The permissions are set to read-only when you check out files initially as read-only (no lock), or are set to user-write (0644) if you check out the file for modification. \
Note that all Check-Ins are "forced" (use the "-f" flag to ci). Even if no changes are done, your file will still be checked in and a new version number assigned to it. When checking in files, regardless of the locking condition, the files are NEVER erased. This is meant to simulate the "ci -u" behavior. If you check the files in as in-progress (keeping the locks), the permissions will continue to include user-write. If you check in the file as finished, the permissions will be changed to read-only.\
Note that the permissions settings are simulating the RCS strict locking mode. If you have binary files and your RCS files have not been set for strict locking, you may have inconsistent permissions between text and uudecoded files.
\b0 MENU ITEMS\
The Project menu controls all the operations surrounding a specific RCS/User project. The RCS Tools menu contains the CheckIn/Out commands unique to a particular RCS project. This menu is also where you change your RCS directories. NOTE: Because NeXT 2.0 does not have Open panels for directories, I had to do some magic. As a result, double-clicking does NOT work in these panels. The Windows menu item is the standard one provided by NeXT. Note that because there is no clean way to free an object when closing the window, the close box is missing. You must close all projects through the Project->Close menu item (or cmd-w). The close command actually closes and frees the currently open project. The Print command
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\fc0 prints the ENTIRE WINDOW. The Services menu item is the standard one provided by NeXT. This menu is provided for NeXT compatibility and serves no real function in this Application.
WHERE EVERYTHING IS SAVED:\
\b0 PREFERENCES\
All preferences are saved using the NXDefaults database. The default preferences are initialized the first time you use CheckItOut. The "owner" is CheckItOut. Note that this is different than the previous version, which used "CheckItOut2" as an owner.\
PROJECT\
The projects are saved anywhere you want. I suggest you save these files under your working project directories. Because CheckItOut recognizes the ".cio" extension, you can double-click on any project file to launch CheckItOut. To delete project files, simply drag them into the recycler.\
\b BACKGROUND INFORMATION:\
\b0 This project was first developed primarily by using system() calls with pre-defined RCS commands built with data gathered through the NeXT panels and windows. Version 2 incorporated the use of a console inside the project window. This was accomplished by a heavy dependence on the NeXT Subprocess example. (This example has a fairly minor bug (fixed by me) which caused endless problems.) Version 3.0 did away with the Subprocess approach, and cleaned up the User Interface. Version 3.0 uses the same basic RCS engine, with tweaks to insure more consistency with RCS, so I am fairly
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\fc0 in its robustness. The application also makes use of the user defaults database provided by NeXT. The global preferences parameters are all saved on quit and loaded at launch time. A special thanks to the abundance of source code provided by NeXT. An extra special thanks to the Internet for providing ideas for my special OpenDirectoryPanel. \
\b BUGS and SUGGESTIONS and pleas for OTHER HELP:\
\pard\b0\fc0 If you want to contact the creator of this program, encounter bugs, or have suggestions for other UNIX programs which should have NeXT tools for them, you may E-mail John Robison at "
\b john@oceania.com
\b0 ".
\pard\tx960\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\fc0 Be sure to spell
\b oceania
\b0 correctly.
\pard\fc0 \
As a past "evaluator" of many shareware programs, I was always
\pard\fc0 to respond if I was not a registered user. I encourage
\b all
\b0 users to respond. If you have anything you think may make the application better, responding can only benefit us all. Note that bugs will be fixed with priority given to
(.txt)